Bundle Upgrade Guide: Version 8.1.0

note

This guide outlines the steps to upgrade Motadata AIOps from version 8.0.13 or any later to version 8.1.0.

note

Ensure TCP ports 9471, 9472, 9473, 9474 are open in Motadata AIOps application bidirectionally to seamlessly upgrade to 8.1.0 version.

Upgrade Patches for 8.1.0

Operating System	Link
Ubuntu/RHEL	Download

Prerequisites for upgrading DB server

Ensure the Motadata AIOps service is not running before you perform this step.

1. Server OS Version Check: If the AIOps server OS version is lower than Ubuntu 24.04, upgrade the OS server before proceeding with the Motadata upgrade.

   OS Upgrade reference: Ubuntu 20.04 to 24.04 Upgrade Guide

2. PostgreSQL Installation (Internet Required): Download the PostgreSQL package for your respective operating system:

   • Postgres for Ubuntu.
   • Postgres for RHEL.

• Extract the package and navigate to the postgres-ubuntu (or respective OS) directory.

• Execute the installation script:

./install.sh

3. Verify PostgreSQL Installation: Run the following command to confirm PostgreSQL is installed successfully:

sudo -u postgres psql

• Check that the PostgreSQL service is active:

systemctl status postgresql

4. Port Requirements: Ensure the following TCP ports (9471, 9472, 9473, 9474, 443) are open bidirectionally for the Motadata AIOps Datastore:

5. Free Disk Space: Ensure at least 60% free disk space on the /motadata partition to perform the patch. (Very Important)

6. Disk IOPS Verification: Verify that the disk IOPS are greater than 250 Mbps before starting the server using the following command:

   sudo dd if=/dev/mapper/vg0-motadata of=test1.img bs=1G count=1 oflag=dsync

7. To upgrade the kernel in the further steps you need to disable the Secure Boot at VM level.

Upgrade Steps

The upgrade steps varies for each deployment type. Please view the steps for your respective deployment architecture mentioned below.

Standalone Deployment

note

Kindly refer Upgrade Guide in case you need to upgrade Ubuntu 20 to Ubuntu 24.

1. Take a VM Snapshot/Backup: Before proceeding with the upgrade, ensure you take a VM snapshot or backup of all servers.

2. Stop Motadata Services: Stop the motadata services for the Observer server, Primary server, Secondary server, Database server, and Collectors.

   service motadata stop

important

If your current Motadata AIOps version is 8.0.25 or 8.0.26, complete the following step before proceeding with the upgrade. First, navigate to the /motadata/motadata/config path and run the below command:

cp motadata bkpmotadata

3. Download AIOPS_UPGRADE.zip: Download and place the AIOPS_UPGRADE.zip file in the /motadata directory on all servers.

4. Unzip the Upgrade Patch:

   unzip AIOPS_UPGRADE.zip

5. Run the Upgrade Script: After unzipping the patch, run the upgrade script:

   sudo ./aiops-upgrade.sh
   note

   If the application and database are on the same server, proceed directly to Step 7. Otherwise, follow Step 6 first, and then move on to Step 7.

important

If you encounter any kernel upgrade-related error during the upgrade process, first complete the upgrade SOP in all servers after that apply below mentioned steps and then reboot respective server.

Steps to Apply the Fix:

1. Log in to the server.

2. Execute the command:

   sudo su

3. Stop the Motadata service.

4. Navigate to:

   cd /home/motadata/

5. Create a directory named Kernel Upgrade.

6. Download file for Kernel Upgrade.

7. Upload the attached .zip files into this directory.

8. Unzip the uploaded file.

9. Execute the following command:

   dpkg -i *.deb

10. Reboot the server to apply the fix.

6. Master App Server Patch:

   • Start the motadata service for the master application server.
   • Wait for the patch to be applied.
   • Verify the patch application by checking the patch-related logs.
   • Ensure the GUI screen for the master server is accessible.

7. Final Steps:

   • Start the motadata service for the database server.
   • Start the motadata service for each collector, one by one.
   • Verify that data is visible on the monitoring screen.

8. Reboot Motadata Servers: After completing the upgrade process, stop the Motadata service on all servers, and then reboot the servers in the following sequence, first App Server then All Other Servers.

   Run the below Command on each server in sequence:

   sudo service motadata stop

   sudo reboot

note

Kindly wait after each reboot until all required services are fully up and running before proceeding to the next server reboot.

Verify the kernel version using the following command:

uname –a

Ensure the output contains: 6.12.39-061239-generic

sudo watch service motadata status

HA Deployment

Pre-Upgrade Validation

note

Kindly refer Upgrade Guide in case you need to upgrade Ubuntu 20 to Ubuntu 24.

note

Ensure there is no data sync backlog among Primary server, Secondary server, and Collector before proceeding to upgrade. Any data yet to be synced will be lost and cannot be recovered.

note

Ensure all servers are up and running. Once all servers are up and running, navigate to Motadata health monitoring screen to ensure all servers are operational and working as intended.

Applying Upgrade Patch

1. Take a VM Snapshot/Backup: Before proceeding with the upgrade, ensure you take a VM snapshot or backup of all servers.

2. Stop Motadata services on all servers in the following sequence: You will required to first stop services on Other Servers, then Primary App Server, and finally the Observer Server.

   sudo service motadata stop 

   sudo service motadata-observer stop

3. Perform a backup of Configuration files for all App servers: Ensure you create a backup for configuration files on all the App server (Primary App and Secondary App).

   sudo cp -r /motadata/motadata/config/ /tmp/ 

4. Remove JSON files from the temporary folder and create a tar file in the Primary App server:

   sudo rm /tmp/config/*json 

   sudo tar -cvf /tmp/config.tar /tmp/config/ 

5. Replicate the Config folder with non-JSON files from Primary App server to other App servers: You will need to copy the config folder containing non-JSON files to Secondary App server.

   sudo scp -r /tmp/config.tar motadata@<App_server_IP>:/tmp/ 

note

Kindly replace the <App_server_IP> placeholder with actual IP address of your App servers.

6. Overwrite the non-JSON files on other App servers: Execute the below-mentioned commands one by one on all other app servers Secondary App server.

   sudo tar -xvf /tmp/config.tar 

   sudo cp /tmp/tmp/config/* /motadata/motadata/config 

important

If your current Motadata AIOps version is 8.0.25 or 8.0.26, complete the following step before proceeding with the upgrade. First, navigate to the /motadata/motadata/config path and run the below command:

cp motadata bkpmotadata

7. Perform the Upgrade on all Servers: You can now start upgrading all servers (Observer, Primary App. Primary DB, Secondary App, Secondary DB, and Collectors)

   • Download AIOPS_UPGRADE.zip: Download and place the AIOPS_UPGRADE.zip file in the /motadata directory on all servers.

   • Unzip the Upgrade Patch:

     unzip AIOPS_UPGRADE.zip

   • Run the Upgrade Script: After unzipping the patch, run the upgrade script:

     sudo ./aiops-upgrade.sh

important

If you encounter any kernel upgrade-related error during the upgrade process, first complete the upgrade SOP in all servers after that apply below mentioned steps and then reboot respective server.

Steps to Apply the Fix:

1. Log in to the server.

2. Execute the command: sudo su

3. Stop the Motadata service.

4. Navigate to: cd /home/motadata/

5. Create a directory named Kernel_Upgrade.

6. Download file for Kernel Upgrade.

7. Upload the attached .zip files into this directory.

8. Unzip the uploaded file.

9. Execute the following command: dpkg -i *.deb

10. Reboot the server to apply the fix.

Post-Upgrade Validation

note

Kindly wait for the motadata-metric-agent-service to spawn on Primary App server before proceeding to next step.

sudo watch service motadata status

8. Start Motadata services on Observer server, Primary App server, and all other servers: Once the upgrade process has been completed, start the services on Motadata Observer server, then Primary App server, and then all other servers in the sequence.

sudo service motadata-observer start

sudo service motadata start

9. Verify all servers are up and running: Once all servers are up and running, navigate to Motadata health monitoring screen to ensure all servers are operational and working as intended.

10. Stop Motadata services on all servers in the following sequence: You will need to stop the services for first Other Servers then Primary App Server and then Observer Server.

sudo service motadata stop

sudo service motadata-observer stop

11. Reboot Motadata Servers: After completing the upgrade process, reboot the Motadata Observer server, then Primary App server, and then all other servers in the sequence.

Command (run on each server in sequence):

sudo reboot

note

Kindly wait after each reboot until all required services are fully up and running before proceeding to the next server reboot. Verify the kernel version using the following command: uname –a Ensure the output contains: 6.12.39-061239-generic

Kindly wait for the motadata-metric-agent-service to spawn on Primary App server before proceeding to next step.

sudo watch service motadata status

HA-DR Deployment

Pre-Upgrade Validation

note

Kindly refer Upgrade Guide in case you need to upgrade Ubuntu 20 to Ubuntu 24.

note

Ensure there is no data sync backlog among Primary server, Secondary server, and Collector before proceeding to upgrade. Any data yet to be synced will be lost and cannot be recovered.

note

Ensure all servers are up and running. Once all servers are up and running, navigate to Motadata health monitoring screen to ensure all servers are operational and working as intended..

Applying Upgrade Patch

1. Take a VM Snapshot/Backup: Before proceeding with the upgrade, ensure you take a VM snapshot or backup of all servers.

2. Stop Motadata services on all servers in the following sequence: You will required to first stop services on Other Servers, then Primary App Server, and finally the Observer Server.

   sudo service motadata stop 

   sudo service motadata-observer stop

3. Perform a backup of Configuration files for all App servers: Ensure you create a backup for configuration files on all the App server (Primary App and Secondary App).

   sudo cp -r /motadata/motadata/config/ /tmp/ 

4. Remove JSON files from the temporary folder and create a tar file in the Primary App server:

   sudo rm /tmp/config/*json 

   sudo tar -cvf /tmp/config.tar /tmp/config/ 

5. Replicate the Config folder with non-JSON files from Primary App server to other App servers: You will need to copy the config folder containing non-JSON files to Secondary App server.

   sudo scp -r /tmp/config.tar motadata@<App_server_IP>:/tmp/ 

note

Kindly replace the <App_server_IP> placeholder with actual IP address of your App servers.

6. Overwrite the non-JSON files on other App servers: Execute the below-mentioned commands one by one on all other app servers Secondary App server.

   sudo tar -xvf /tmp/config.tar 

   sudo cp /tmp/tmp/config/* /motadata/motadata/config 

important

If your current Motadata AIOps version is 8.0.25 or 8.0.26, complete the following step before proceeding with the upgrade. First, navigate to the /motadata/motadata/config path and run the below command:

cp motadata bkpmotadata

7. Perform the Upgrade on all Servers: You can now start upgrading all servers (Observer, Primary App. Primary DB, Secondary App, Secondary DB, and Collectors)

   • Download AIOPS_UPGRADE.zip: Download and place the AIOPS_UPGRADE.zip file in the /motadata directory on all servers.

   • Unzip the Upgrade Patch:

     unzip AIOPS_UPGRADE.zip

   • Run the Upgrade Script: After unzipping the patch, run the upgrade script:

     sudo ./aiops-upgrade.sh

important

If you encounter any kernel upgrade-related error during the upgrade process, first complete the upgrade SOP in all servers after that apply below mentioned steps and then reboot respective server.

Steps to Apply the Fix:

1. Log in to the server.

2. Execute the command: sudo su

3. Stop the Motadata service.

4. Navigate to: cd /home/motadata/

5. Create a directory named Kernel_Upgrade.

6. Download file for Kernel Upgrade.

7. Upload the attached .zip files into this directory.

8. Unzip the uploaded file.

9. Execute the following command: dpkg -i *.deb

10. Reboot the server to apply the fix.

Post-Upgrade Validation

note

Kindly wait for the motadata-metric-agent-service to spawn on Primary App server before proceeding to next step.

sudo watch service motadata status

8. Start Motadata services on Observer server, Primary App server, and all other servers: Once the upgrade process has been completed, start the services on Motadata Observer server, then Primary App server, and then all other servers in the sequence.

sudo service motadata-observer start

sudo service motadata start

9. Verify all servers are up and running: Once all servers are up and running, navigate to Motadata health monitoring screen to ensure all servers are operational and working as intended.

10. Stop Motadata services on all servers in the following sequence: You will need to stop the services for first Other Servers then Primary App Server and then Observer Server.

sudo service motadata stop

sudo service motadata-observer stop

11. Reboot Motadata Servers: After completing the upgrade process, reboot the Motadata Observer server, then Primary App server, and then all other servers in the sequence.

Command (run on each server in sequence):

sudo reboot

note

Kindly wait after each reboot until all required services are fully up and running before proceeding to the next server reboot. Verify the kernel version using the following command: uname –a Ensure the output contains: 6.12.39-061239-generic

Kindly wait for the motadata-metric-agent-service to spawn on Primary App server before proceeding to next step.

sudo watch service motadata status